Fix for Copying Screener Automations and Engagements

Amplify Screen

We fixed an issue where users couldn’t copy Screener Automations or Screener Engagements without encountering an error. All copy paths now work as expected, including copying an automation containing a Screener step, copying a Screener Engagement directly, and importing an automation that includes a Screener step.

Users can now reliably repurpose existing screeners without rebuilding them from scratch, which also helps unblock Amplify customers who are migrating automations from custom screening fields to the new standard ATS fields.